Skip to content

[12.x] Add support for APP_LOCAL_SITES_PATH and APP_REMOTE_SITES_PATH to map to editor file paths #56264

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: 12.x
Choose a base branch
from

Conversation

iammursal
Copy link

@iammursal iammursal commented Jul 10, 2025

Fixes #56185

Summary

This PR introduces support for two environment variables:

  • APP_LOCAL_SITES_PATH
  • APP_REMOTE_SITES_PATH

These allow mapping container paths to host paths in editor links shown on Laravel’s exception pages, similar to the IGNITION_LOCAL_SITES_PATH and IGNITION_REMOTE_SITES_PATH previously available via Ignition.

Use Case

When Laravel is running inside a Docker container, file paths shown in error pages point to the container’s file system (/var/www/html/...), which does not exist on the host machine. This makes editor links like vscode://file/... fail to open.

With this feature, developers can map paths:

APP_LOCAL_SITES_PATH=/Users/dev/code/myapp
APP_REMOTE_SITES_PATH=/var/www/html

… to map editor file paths

Update ResolvesDumpSource.php

Update ResolvesDumpSourceTest.php

Update ResolvesDumpSource.php

Update ResolvesDumpSource.php

Update ResolvesDumpSourceTest.php
@iammursal iammursal force-pushed the fix/editor-path-mapping branch from b95217d to ace5829 Compare July 10, 2025 20:07
@iammursal iammursal changed the title [12.x] Add support for APP_LOCAL_SITES_PATH and APP_REMOTE_SITES_PATH… [12.x] Add support for APP_LOCAL_SITES_PATH and APP_REMOTE_SITES_PATH to map to editor file paths Jul 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Errors inside Docker container have Docker path, not host path
1 participant